win32: Don't check the position of a NULL device
authorCarlos Garnacho <carlosg@gnome.org>
Tue, 27 Jan 2015 11:24:18 +0000 (11:24 +0000)
committerCarlos Garnacho <carlosg@gnome.org>
Wed, 28 Jan 2015 16:59:29 +0000 (16:59 +0000)
commitea983404ec02c1fcb01be13eb2ce271430d80346
treee6716213e68ccbac2603ac01ff60f853fb81f07f
parent15438905693106e81b96100ce5843e87910768d5
win32: Don't check the position of a NULL device

This function is given a barely setup GdkEvent, so the GdkDevice field
is still unset, causing warnings and misbehaviors when the position
is queried for it.

Given that the wintab GTK+ code seems to rely somewhat hard on the wintab
device managing the pointer cursor, query the pointer position from the
pointer itself.

https://bugzilla.gnome.org/show_bug.cgi?id=743330
gdk/win32/gdkdevicemanager-win32.c